Trimming video within a messaging system

ABSTRACT

Aspects of the present disclosure involve a system comprising a computer-readable storage medium storing a program and method for trimming video. The program and method provide for providing a capture user interface for capturing a video to generate a media content item; displaying a preview user interface for previewing and editing the captured video to generate the media content item, the preview user interface including an interface element for selecting to trim the captured video or to set a playback option for the media content item; receiving, via the interface element, user input selecting to trim the captured video; and displaying a preview bar within the preview user interface, the preview bar including a set of frames of the captured video and front and back handles respectively positioned in front and in back of the set of frames, each of the front and back handles being selectable to trim video.

CROSS-REFERENCE TO RELATED APPLICATION

This patent application claims the benefit of U.S. Provisional PatentApplication No. 63/131,634, filed Dec. 29, 2020, entitled “TRIMMINGVIDEO WITHIN A MESSAGING SYSTEM”, which is incorporated by referenceherein in its entirety.

TECHNICAL FIELD

The present disclosure relates generally to a messaging system,including trimming video within a messaging system.

BACKGROUND

Messaging systems provide for the exchange of message content betweenusers. For example, a messaging system allows a user to exchange messagecontent (e.g., text, videos) with one or more other users.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

In the drawings, which are not necessarily drawn to scale, like numeralsmay describe similar components in different views. To easily identifythe discussion of any particular element or act, the most significantdigit or digits in a reference number refer to the figure number inwhich that element is first introduced. Some nonlimiting examples areillustrated in the figures of the accompanying drawings in which:

FIG. 1 is a diagrammatic representation of a networked environment inwhich the present disclosure may be deployed, in accordance with someexamples.

FIG. 2 is a diagrammatic representation of a messaging system, inaccordance with some examples, that has both client-side and server-sidefunctionality.

FIG. 3 is a diagrammatic representation of a data structure asmaintained in a database, in accordance with some examples.

FIG. 4 is a diagrammatic representation of a message, in accordance withsome examples.

FIG. 5 is a diagram illustrating a user interface arrangement configuredto capture, preview and edit video, in accordance with some exampleembodiments.

FIGS. 6A-6C illustrate a user interface for trimming captured video togenerate a media content item, in accordance with some exampleembodiments.

FIG. 7 is a flowchart illustrating a process for trimming video within amessaging system, in accordance with some example embodiments.

FIG. 8 is a flowchart for an access-limiting process, in accordance withsome examples.

FIG. 9 is a diagrammatic representation of a machine in the form of acomputer system within which a set of instructions may be executed forcausing the machine to perform any one or more of the methodologiesdiscussed herein, in accordance with some examples.

FIG. 10 is a block diagram showing a software architecture within whichexamples may be implemented.

DETAILED DESCRIPTION

A messaging system typically allow users to exchange content items(e.g., messages, images and/or video) with one another in a messagethread. For example, a messaging system allows a user to exchangemessage content (e.g., text, videos) with one or more other users.

The disclosed embodiments provide a messaging system with user interfaceelements to trim captured video in order to generate a media contentitem. After a video is captured within a capture user interface, themessaging system displays a preview user interface for previewing andediting the captured video. The preview user interface includes aninterface element (e.g., a button) for selecting from among multipleplayback options for the media content item. The playback optionsinclude looping playback, bouncing playback or single playback. Inaddition to the playback options, the interface element within thepreview user interface includes an option to trim the captured video.

In response to user selection of the trim option, the preview userinterface presents a preview bar with frames (e.g., thumbnails) thatrepresent the video. The preview bar is presented with front and backhandles for trimming the video, and a splitting element for splittingthe captured video into separate video clips. Each separate video clipis in turn presented with respective front and back handles and/orsplitting elements for trimming or splitting the individual video clip.

FIG. 1 is a block diagram showing an example messaging system 100 forexchanging data (e.g., messages and associated content) over a network.The messaging system 100 includes multiple instances of a client device102, each of which hosts a number of applications, including a messagingclient 104 and other applications 106. Each messaging client 104 iscommunicatively coupled to other instances of the messaging client 104(e.g., hosted on respective other client devices 102), a messagingserver system 108 and third-party servers 110 via a network 112 (e.g.,the Internet). A messaging client 104 can also communicate withlocally-hosted applications 106 using Applications Program Interfaces(APIs).

A messaging client 104 is able to communicate and exchange data withother messaging clients 104 and with the messaging server system 108 viathe network 112. The data exchanged between messaging clients 104, andbetween a messaging client 104 and the messaging server system 108,includes functions (e.g., commands to invoke functions) as well aspayload data (e.g., text, audio, video or other multimedia data).

The messaging server system 108 provides server-side functionality viathe network 112 to a particular messaging client 104. While certainfunctions of the messaging system 100 are described herein as beingperformed by either a messaging client 104 or by the messaging serversystem 108, the location of certain functionality either within themessaging client 104 or the messaging server system 108 may be a designchoice. For example, it may be technically preferable to initiallydeploy certain technology and functionality within the messaging serversystem 108 but to later migrate this technology and functionality to themessaging client 104 where a client device 102 has sufficient processingcapacity.

The messaging server system 108 supports various services and operationsthat are provided to the messaging client 104. Such operations includetransmitting data to, receiving data from, and processing data generatedby the messaging client 104. This data may include message content,client device information, geolocation information, media augmentationand overlays, message content persistence conditions, social networkinformation, and live event information, as examples. Data exchangeswithin the messaging system 100 are invoked and controlled throughfunctions available via user interfaces (UIs) of the messaging client104.

Turning now specifically to the messaging server system 108, anApplication Program Interface (API) server 116 is coupled to, andprovides a programmatic interface to, application servers 114. Theapplication servers 114 are communicatively coupled to a database server120, which facilitates access to a database 126 that stores dataassociated with messages processed by the application servers 114.Similarly, a web server 128 is coupled to the application servers 114,and provides web-based interfaces to the application servers 114. Tothis end, the web server 128 processes incoming network requests overthe Hypertext Transfer Protocol (HTTP) and several other relatedprotocols.

The Application Program Interface (API) server 116 receives andtransmits message data (e.g., commands and message payloads) between theclient device 102 and the application servers 114. Specifically, theApplication Program Interface (API) server 116 provides a set ofinterfaces (e.g., routines and protocols) that can be called or queriedby the messaging client 104 in order to invoke functionality of theapplication servers 114. The Application Program Interface (API) server116 exposes various functions supported by the application servers 114,including account registration, login functionality, the sending ofmessages, via the application servers 114, from a particular messagingclient 104 to another messaging client 104, the sending of media files(e.g., images or video) from a messaging client 104 to a messagingserver 118, and for possible access by another messaging client 104, thesettings of a collection of media data (e.g., story), the retrieval of alist of friends of a user of a client device 102, the retrieval of suchcollections, the retrieval of messages and content, the addition anddeletion of entities (e.g., friends) to an entity graph (e.g., a socialgraph), the location of friends within a social graph, and opening anapplication event (e.g., relating to the messaging client 104).

The application servers 114 host a number of server applications andsubsystems, including for example a messaging server 118, an imageprocessing server 122, and a social network server 124. The messagingserver 118 implements a number of message processing technologies andfunctions, particularly related to the aggregation and other processingof content (e.g., textual and multimedia content) included in messagesreceived from multiple instances of the messaging client 104. As will bedescribed in further detail, the text and media content from multiplesources may be aggregated into collections of content (e.g., calledstories or galleries). These collections are then made available to themessaging client 104. Other processor and memory intensive processing ofdata may also be performed server-side by the messaging server 118, inview of the hardware requirements for such processing.

The application servers 114 also include an image processing server 122that is dedicated to performing various image processing operations,typically with respect to images or video within the payload of amessage sent from or received at the messaging server 118.

The social network server 124 supports various social networkingfunctions and services and makes these functions and services availableto the messaging server 118. To this end, the social network server 124maintains and accesses an entity graph 304 (as shown in FIG. 3 ) withinthe database 126. Examples of functions and services supported by thesocial network server 124 include the identification of other users ofthe messaging system 100 with which a particular user has relationshipsor is “following,” and also the identification of other entities andinterests of a particular user.

Returning to the messaging client 104, features and functions of anexternal resource (e.g., an application 106 or applet) are madeavailable to a user via an interface of the messaging client 104. Inthis context, “external” refers to the fact that the application 106 orapplet is external to the messaging client 104. The external resource isoften provided by a third party but may also be provided by the creatoror provider of the messaging client 104. The messaging client 104receives a user selection of an option to launch or access features ofsuch an external resource. The external resource may be the application106 installed on the client device 102 (e.g., a “native app”), or asmall-scale version of the application (e.g., an “applet”) that ishosted on the client device 102 or remote of the client device 102(e.g., on third-party servers 110). The small-scale version of theapplication includes a subset of features and functions of theapplication (e.g., the full-scale, native version of the application)and is implemented using a markup-language document. In one example, thesmall-scale version of the application (e.g., an “applet”) is aweb-based, markup-language version of the application and is embedded inthe messaging client 104. In addition to using markup-language documents(e.g., a .*ml file), an applet may incorporate a scripting language(e.g., a .*js file or a .json file) and a style sheet (e.g., a .*ssfile).

In response to receiving a user selection of the option to launch oraccess features of the external resource, the messaging client 104determines whether the selected external resource is a web-basedexternal resource or a locally-installed application 106. In some cases,applications 106 that are locally installed on the client device 102 canbe launched independently of and separately from the messaging client104, such as by selecting an icon, corresponding to the application 106,on a home screen of the client device 102. Small-scale versions of suchapplications can be launched or accessed via the messaging client 104and, in some examples, no or limited portions of the small-scaleapplication can be accessed outside of the messaging client 104. Thesmall-scale application can be launched by the messaging client 104receiving, from a third-party server 110 for example, a markup-languagedocument associated with the small-scale application and processing sucha document.

In response to determining that the external resource is alocally-installed application 106, the messaging client 104 instructsthe client device 102 to launch the external resource by executinglocally-stored code corresponding to the external resource. In responseto determining that the external resource is a web-based resource, themessaging client 104 communicates with the third-party servers 110 (forexample) to obtain a markup-language document corresponding to theselected external resource. The messaging client 104 then processes theobtained markup-language document to present the web-based externalresource within a user interface of the messaging client 104.

The messaging client 104 can notify a user of the client device 102, orother users related to such a user (e.g., “friends”), of activity takingplace in one or more external resources. For example, the messagingclient 104 can provide participants in a conversation (e.g., a chatsession) in the messaging client 104 with notifications relating to thecurrent or recent use of an external resource by one or more members ofa group of users. One or more users can be invited to join in an activeexternal resource or to launch a recently-used but currently inactive(in the group of friends) external resource. The external resource canprovide participants in a conversation, each using respective messagingclients 104, with the ability to share an item, status, state, orlocation in an external resource with one or more members of a group ofusers into a chat session. The shared item may be an interactive chatcard with which members of the chat can interact, for example, to launchthe corresponding external resource, view specific information withinthe external resource, or take the member of the chat to a specificlocation or state within the external resource. Within a given externalresource, response messages can be sent to users on the messaging client104. The external resource can selectively include different media itemsin the responses, based on a current context of the external resource.

The messaging client 104 can present a list of the available externalresources (e.g., applications 106 or applets) to a user to launch oraccess a given external resource. This list can be presented in acontext-sensitive menu. For example, the icons representing differentones of the application 106 (or applets) can vary based on how the menuis launched by the user (e.g., from a conversation interface or from anon-conversation interface).

FIG. 2 is a block diagram illustrating further details regarding themessaging system 100, according to some examples. Specifically, themessaging system 100 is shown to comprise the messaging client 104 andthe application servers 114. The messaging system 100 embodies a numberof subsystems, which are supported on the client-side by the messagingclient 104 and on the sever-side by the application servers 114. Thesesubsystems include, for example, an ephemeral timer system 202, acollection management system 204, an augmentation system 208, a mapsystem 210, and an external resource system 212.

The ephemeral timer system 202 is responsible for enforcing thetemporary or time-limited access to content by the messaging client 104and the messaging server 118. The ephemeral timer system 202incorporates a number of timers that, based on duration and displayparameters associated with a message, or collection of messages (e.g., astory), selectively enable access (e.g., for presentation and display)to messages and associated content via the messaging client 104. Furtherdetails regarding the operation of the ephemeral timer system 202 areprovided below.

The collection management system 204 is responsible for managing sets orcollections of media (e.g., collections of text, image video, and audiodata). A collection of content (e.g., messages, including images, video,text, and audio) may be organized into an “event gallery” or an “eventstory.” Such a collection may be made available for a specified timeperiod, such as the duration of an event to which the content relates.For example, content relating to a music concert may be made availableas a “story” for the duration of that music concert. The collectionmanagement system 204 may also be responsible for publishing an iconthat provides notification of the existence of a particular collectionto the user interface of the messaging client 104.

The collection management system 204 furthermore includes a curationinterface 206 that allows a collection manager to manage and curate aparticular collection of content. For example, the curation interface206 enables an event organizer to curate a collection of contentrelating to a specific event (e.g., delete inappropriate content orredundant messages). Additionally, the collection management system 204employs machine vision (or image recognition technology) and contentrules to automatically curate a content collection. In certain examples,compensation may be paid to a user for the inclusion of user-generatedcontent into a collection. In such cases, the collection managementsystem 204 operates to automatically make payments to such users for theuse of their content.

The augmentation system 208 provides various functions that enable auser to augment (e.g., annotate or otherwise modify or edit) mediacontent associated with a message. For example, the augmentation system208 provides functions related to the generation and publishing of mediaoverlays for messages processed by the messaging system 100. Theaugmentation system 208 operatively supplies a media overlay oraugmentation (e.g., an image filter) to the messaging client 104 basedon a geolocation of the client device 102. In another example, theaugmentation system 208 operatively supplies a media overlay to themessaging client 104 based on other information, such as social networkinformation of the user of the client device 102. A media overlay mayinclude audio and visual content and visual effects. Examples of audioand visual content include pictures, texts, logos, animations, and soundeffects. An example of a visual effect includes color overlaying. Theaudio and visual content or the visual effects can be applied to a mediacontent item (e.g., a photo) at the client device 102. For example, themedia overlay may include text or image that can be overlaid on top of aphotograph taken by the client device 102. In another example, the mediaoverlay includes an identification of a location overlay (e.g., Venicebeach), a name of a live event, or a name of a merchant overlay (e.g.,Beach Coffee House). In another example, the augmentation system 208uses the geolocation of the client device 102 to identify a mediaoverlay that includes the name of a merchant at the geolocation of theclient device 102. The media overlay may include other indiciaassociated with the merchant. The media overlays may be stored in thedatabase 126 and accessed through the database server 120.

In some examples, the augmentation system 208 provides a user-basedpublication platform that enables users to select a geolocation on a mapand upload content associated with the selected geolocation. The usermay also specify circumstances under which a particular media overlayshould be offered to other users. The augmentation system 208 generatesa media overlay that includes the uploaded content and associates theuploaded content with the selected geolocation.

In other examples, the augmentation system 208 provides a merchant-basedpublication platform that enables merchants to select a particular mediaoverlay associated with a geolocation via a bidding process. Forexample, the augmentation system 208 associates the media overlay of thehighest bidding merchant with a corresponding geolocation for apredefined amount of time.

In other examples, as discussed below with respect to FIG. 3 , theaugmentation system 208 provides for presenting augmented realitycontent in association with an image or a video captured by a camera ofthe client device 102. The augmentation system 208 may implement orotherwise access augmented reality content items (e.g., corresponding toapplying Lenses or augmented reality experiences) for providingreal-time special effect(s) and/or sound(s) that may be added to theimage or video. To facilitate the presentation of augmented realitycontent, the augmentation system 208 may implement or otherwise accessobject recognition algorithms (e.g., including machine learningalgorithms) configured to scan an image or video, and to detect/trackthe movement of objects within the image or video.

The map system 210 provides various geographic location functions, andsupports the presentation of map-based media content and messages by themessaging client 104. For example, the map system 210 enables thedisplay of user icons or avatars (e.g., stored in profile data 302) on amap to indicate a current or past location of “friends” of a user, aswell as media content (e.g., collections of messages includingphotographs and videos) generated by such friends, within the context ofa map. For example, a message posted by a user to the messaging system100 from a specific geographic location may be displayed within thecontext of a map at that particular location to “friends” of a specificuser on a map interface of the messaging client 104. A user canfurthermore share his or her location and status information (e.g.,using an appropriate status avatar) with other users of the messagingsystem 100 via the messaging client 104, with this location and statusinformation being similarly displayed within the context of a mapinterface of the messaging client 104 to selected users.

The external resource system 212 provides an interface for the messagingclient 104 to communicate with remote servers (e.g. third-party servers110) to launch or access external resources, i.e. applications orapplets. Each third-party server 110 hosts, for example, a markuplanguage (e.g., HTML5) based application or small-scale version of anapplication (e.g., game, utility, payment, or ride-sharing application).The messaging client 104 may launches a web-based resource (e.g.,application) by accessing the HTML5 file from the third-party servers110 associated with the web-based resource. In certain examples,applications hosted by third-party servers 110 are programmed inJavaScript leveraging a Software Development Kit (SDK) provided by themessaging server 118. The SDK includes Application ProgrammingInterfaces (APIs) with functions that can be called or invoked by theweb-based application. In certain examples, the messaging server 118includes a JavaScript library that provides a given external resourceaccess to certain user data of the messaging client 104. HTML5 is usedas an example technology for programming games, but applications andresources programmed based on other technologies can be used.

In order to integrate the functions of the SDK into the web-basedresource, the SDK is downloaded by a third-party server 110 from themessaging server 118 or is otherwise received by the third-party server110. Once downloaded or received, the SDK is included as part of theapplication code of a web-based external resource. The code of theweb-based resource can then call or invoke certain functions of the SDKto integrate features of the messaging client 104 into the web-basedresource.

The SDK stored on the messaging server 118 effectively provides thebridge between an external resource (e.g., applications 106 or appletsand the messaging client 104. This provides the user with a seamlessexperience of communicating with other users on the messaging client104, while also preserving the look and feel of the messaging client104. To bridge communications between an external resource and amessaging client 104, in certain examples, the SDK facilitatescommunication between third-party servers 110 and the messaging client104. In certain examples, a Web ViewJavaScriptBridge running on a clientdevice 102 establishes two one-way communication channels between anexternal resource and the messaging client 104. Messages are sentbetween the external resource and the messaging client 104 via thesecommunication channels asynchronously. Each SDK function invocation issent as a message and callback. Each SDK function is implemented byconstructing a unique callback identifier and sending a message withthat callback identifier.

By using the SDK, not all information from the messaging client 104 isshared with third-party servers 110. The SDK limits which information isshared based on the needs of the external resource. In certain examples,each third-party server 110 provides an HTML5 file corresponding to theweb-based external resource to the messaging server 118. The messagingserver 118 can add a visual representation (such as a box art or othergraphic) of the web-based external resource in the messaging client 104.Once the user selects the visual representation or instructs themessaging client 104 through a GUI of the messaging client 104 to accessfeatures of the web-based external resource, the messaging client 104obtains the HTML5 file and instantiates the resources necessary toaccess the features of the web-based external resource.

The messaging client 104 presents a graphical user interface (e.g., alanding page or title screen) for an external resource. During, before,or after presenting the landing page or title screen, the messagingclient 104 determines whether the launched external resource has beenpreviously authorized to access user data of the messaging client 104.In response to determining that the launched external resource has beenpreviously authorized to access user data of the messaging client 104,the messaging client 104 presents another graphical user interface ofthe external resource that includes functions and features of theexternal resource. In response to determining that the launched externalresource has not been previously authorized to access user data of themessaging client 104, after a threshold period of time (e.g., 3 seconds)of displaying the landing page or title screen of the external resource,the messaging client 104 slides up (e.g., animates a menu as surfacingfrom a bottom of the screen to a middle of or other portion of thescreen) a menu for authorizing the external resource to access the userdata. The menu identifies the type of user data that the externalresource will be authorized to use. In response to receiving a userselection of an accept option, the messaging client 104 adds theexternal resource to a list of authorized external resources and allowsthe external resource to access user data from the messaging client 104.In some examples, the external resource is authorized by the messagingclient 104 to access the user data in accordance with an OAuth 2framework.

The messaging client 104 controls the type of user data that is sharedwith external resources based on the type of external resource beingauthorized. For example, external resources that include full-scaleapplications (e.g., an application 106) are provided with access to afirst type of user data (e.g., only two-dimensional avatars of userswith or without different avatar characteristics). As another example,external resources that include small-scale versions of applications(e.g., web-based versions of applications) are provided with access to asecond type of user data (e.g., payment information, two-dimensionalavatars of users, three-dimensional avatars of users, and avatars withvarious avatar characteristics). Avatar characteristics includedifferent ways to customize a look and feel of an avatar, such asdifferent poses, facial features, clothing, and so forth.

FIG. 3 is a schematic diagram illustrating data structures 300, whichmay be stored in the database 126 of the messaging server system 108,according to certain examples. While the content of the database 126 isshown to comprise a number of tables, it will be appreciated that thedata could be stored in other types of data structures (e.g., as anobject-oriented database).

The database 126 includes message data stored within a message table306. This message data includes, for any particular one message, atleast message sender data, message recipient (or receiver) data, and apayload. Further details regarding information that may be included in amessage, and included within the message data stored in the messagetable 306 is described below with reference to FIG. 4 .

An entity table 308 stores entity data, and is linked (e.g.,referentially) to an entity graph 304 and profile data 302. Entities forwhich records are maintained within the entity table 308 may includeindividuals, corporate entities, organizations, objects, places, events,and so forth. Regardless of entity type, any entity regarding which themessaging server system 108 stores data may be a recognized entity. Eachentity is provided with a unique identifier, as well as an entity typeidentifier (not shown).

The entity graph 304 stores information regarding relationships andassociations between entities. Such relationships may be social,professional (e.g., work at a common corporation or organization)interested-based or activity-based, merely for example.

The profile data 302 stores multiple types of profile data about aparticular entity. The profile data 302 may be selectively used andpresented to other users of the messaging system 100, based on privacysettings specified by a particular entity. Where the entity is anindividual, the profile data 302 includes, for example, a user name,telephone number, address, settings (e.g., notification and privacysettings), as well as a user-selected avatar representation (orcollection of such avatar representations). A particular user may thenselectively include one or more of these avatar representations withinthe content of messages communicated via the messaging system 100, andon map interfaces displayed by messaging clients 104 to other users. Thecollection of avatar representations may include “status avatars,” whichpresent a graphical representation of a status or activity that the usermay select to communicate at a particular time.

Where the entity is a group, the profile data 302 for the group maysimilarly include one or more avatar representations associated with thegroup, in addition to the group name, members, and various settings(e.g., notifications) for the relevant group.

The database 126 also stores augmentation data, such as overlays orfilters, in an augmentation table 310. The augmentation data isassociated with and applied to videos (for which data is stored in avideo table 314) and images (for which data is stored in an image table316).

Filters, in one example, are overlays that are displayed as overlaid onan image or video during presentation to a recipient user. Filters maybe of various types, including user-selected filters from a set offilters presented to a sending user by the messaging client 104 when thesending user is composing a message. Other types of filters includegeolocation filters (also known as geo-filters), which may be presentedto a sending user based on geographic location. For example, geolocationfilters specific to a neighborhood or special location may be presentedwithin a user interface by the messaging client 104, based ongeolocation information determined by a Global Positioning System (GPS)unit of the client device 102.

Another type of filter is a data filter, which may be selectivelypresented to a sending user by the messaging client 104, based on otherinputs or information gathered by the client device 102 during themessage creation process. Examples of data filters include currenttemperature at a specific location, a current speed at which a sendinguser is traveling, battery life for a client device 102, or the currenttime.

Other augmentation data that may be stored within the image table 316includes augmented reality content items (e.g., corresponding toapplying Lenses or augmented reality experiences). An augmented realitycontent item may provide a real-time special effect and/or sound thatmay be added to an image or a video.

As described above, augmentation data includes augmented reality contentitems, overlays, image transformations, AR images, and similar termsrefer to modifications that may be applied to image data (e.g., videosor images). This includes real-time modifications, which modify an imageas it is captured using device sensors (e.g., one or multiple cameras)of a client device 102 and then displayed on a screen of the clientdevice 102 with the modifications. This also includes modifications tostored content, such as video clips in a gallery that may be modified.For example, in a client device 102 with access to multiple augmentedreality content items, a user can use a single video clip with multipleaugmented reality content items to see how the different augmentedreality content items will modify the stored clip. For example, multipleaugmented reality content items that apply different pseudorandommovement models can be applied to the same content by selectingdifferent augmented reality content items for the content. Similarly,real-time video capture may be used with an illustrated modification toshow how video images currently being captured by sensors of a clientdevice 102 would modify the captured data. Such data may simply bedisplayed on the screen and not stored in memory, or the contentcaptured by the device sensors may be recorded and stored in memory withor without the modifications (or both). In some systems, a previewfeature can show how different augmented reality content items will lookwithin different windows in a display at the same time. This can, forexample, enable multiple windows with different pseudorandom animationsto be viewed on a display at the same time.

Data and various systems using augmented reality content items or othersuch transform systems to modify content using this data can thusinvolve detection of objects (e.g., faces, hands, bodies, cats, dogs,surfaces, objects, etc.), tracking of such objects as they leave, enter,and move around the field of view in video frames, and the modificationor transformation of such objects as they are tracked. In variousexamples, different methods for achieving such transformations may beused. Some examples may involve generating a three-dimensional meshmodel of the object or objects, and using transformations and animatedtextures of the model within the video to achieve the transformation. Inother examples, tracking of points on an object may be used to place animage or texture (which may be two dimensional or three dimensional) atthe tracked position. In still further examples, neural network analysisof video frames may be used to place images, models, or textures incontent (e.g., images or frames of video). Augmented reality contentitems thus refer both to the images, models, and textures used to createtransformations in content, as well as to additional modeling andanalysis information needed to achieve such transformations with objectdetection, tracking, and placement.

Real-time video processing can be performed with any kind of video data(e.g., video streams, video files, etc.) saved in a memory of acomputerized system of any kind. For example, a user can load videofiles and save them in a memory of a device, or can generate a videostream using sensors of the device. Additionally, any objects can beprocessed using a computer animation model, such as a human's face andparts of a human body, animals, or non-living things such as chairs,cars, or other objects.

In some examples, when a particular modification is selected along withcontent to be transformed, elements to be transformed are identified bythe computing device, and then detected and tracked if they are presentin the frames of the video. The elements of the object are modifiedaccording to the request for modification, thus transforming the framesof the video stream. Transformation of frames of a video stream can beperformed by different methods for different kinds of transformation.For example, for transformations of frames mostly referring to changingforms of object's elements characteristic points for each element of anobject are calculated (e.g., using an Active Shape Model (ASM) or otherknown methods). Then, a mesh based on the characteristic points isgenerated for each of the at least one element of the object. This meshused in the following stage of tracking the elements of the object inthe video stream. In the process of tracking, the mentioned mesh foreach element is aligned with a position of each element. Then,additional points are generated on the mesh. A first set of first pointsis generated for each element based on a request for modification, and aset of second points is generated for each element based on the set offirst points and the request for modification. Then, the frames of thevideo stream can be transformed by modifying the elements of the objecton the basis of the sets of first and second points and the mesh. Insuch method, a background of the modified object can be changed ordistorted as well by tracking and modifying the background.

In some examples, transformations changing some areas of an object usingits elements can be performed by calculating characteristic points foreach element of an object and generating a mesh based on the calculatedcharacteristic points. Points are generated on the mesh, and thenvarious areas based on the points are generated. The elements of theobject are then tracked by aligning the area for each element with aposition for each of the at least one element, and properties of theareas can be modified based on the request for modification, thustransforming the frames of the video stream. Depending on the specificrequest for modification properties of the mentioned areas can betransformed in different ways. Such modifications may involve changingcolor of areas; removing at least some part of areas from the frames ofthe video stream; including one or more new objects into areas which arebased on a request for modification; and modifying or distorting theelements of an area or object. In various examples, any combination ofsuch modifications or other similar modifications may be used. Forcertain models to be animated, some characteristic points can beselected as control points to be used in determining the entirestate-space of options for the model animation.

In some examples of a computer animation model to transform image datausing face detection, the face is detected on an image with use of aspecific face detection algorithm (e.g., Viola-Jones). Then, an ActiveShape Model (ASM) algorithm is applied to the face region of an image todetect facial feature reference points.

Other methods and algorithms suitable for face detection can be used.For example, in some examples, features are located using a landmark,which represents a distinguishable point present in most of the imagesunder consideration. For facial landmarks, for example, the location ofthe left eye pupil may be used. If an initial landmark is notidentifiable (e.g., if a person has an eyepatch), secondary landmarksmay be used. Such landmark identification procedures may be used for anysuch objects. In some examples, a set of landmarks forms a shape. Shapescan be represented as vectors using the coordinates of the points in theshape. One shape is aligned to another with a similarity transform(allowing translation, scaling, and rotation) that minimizes the averageEuclidean distance between shape points. The mean shape is the mean ofthe aligned training shapes.

In some examples, a search for landmarks from the mean shape aligned tothe position and size of the face determined by a global face detectoris started. Such a search then repeats the steps of suggesting atentative shape by adjusting the locations of shape points by templatematching of the image texture around each point and then conforming thetentative shape to a global shape model until convergence occurs. Insome systems, individual template matches are unreliable, and the shapemodel pools the results of the weak template matches to form a strongeroverall classifier. The entire search is repeated at each level in animage pyramid, from coarse to fine resolution.

A transformation system can capture an image or video stream on a clientdevice (e.g., the client device 102) and perform complex imagemanipulations locally on the client device 102 while maintaining asuitable user experience, computation time, and power consumption. Thecomplex image manipulations may include size and shape changes, emotiontransfers (e.g., changing a face from a frown to a smile), statetransfers (e.g., aging a subject, reducing apparent age, changinggender), style transfers, graphical element application, and any othersuitable image or video manipulation implemented by a convolutionalneural network that has been configured to execute efficiently on theclient device 102.

In some examples, a computer animation model to transform image data canbe used by a system where a user may capture an image or video stream ofthe user (e.g., a selfie) using a client device 102 having a neuralnetwork operating as part of a messaging client 104 operating on theclient device 102. The transformation system operating within themessaging client 104 determines the presence of a face within the imageor video stream and provides modification icons associated with acomputer animation model to transform image data, or the computeranimation model can be present as associated with an interface describedherein. The modification icons include changes that may be the basis formodifying the user's face within the image or video stream as part ofthe modification operation. Once a modification icon is selected, thetransform system initiates a process to convert the image of the user toreflect the selected modification icon (e.g., generate a smiling face onthe user). A modified image or video stream may be presented in agraphical user interface displayed on the client device 102 as soon asthe image or video stream is captured, and a specified modification isselected. The transformation system may implement a complexconvolutional neural network on a portion of the image or video streamto generate and apply the selected modification. That is, the user maycapture the image or video stream and be presented with a modifiedresult in real-time or near real-time once a modification icon has beenselected. Further, the modification may be persistent while the videostream is being captured, and the selected modification icon remainstoggled. Machine taught neural networks may be used to enable suchmodifications.

The graphical user interface, presenting the modification performed bythe transform system, may supply the user with additional interactionoptions. Such options may be based on the interface used to initiate thecontent capture and selection of a particular computer animation model(e.g., initiation from a content creator user interface). In variousexamples, a modification may be persistent after an initial selection ofa modification icon. The user may toggle the modification on or off bytapping or otherwise selecting the face being modified by thetransformation system and store it for later viewing or browse to otherareas of the imaging application. Where multiple faces are modified bythe transformation system, the user may toggle the modification on oroff globally by tapping or selecting a single face modified anddisplayed within a graphical user interface. In some examples,individual faces, among a group of multiple faces, may be individuallymodified, or such modifications may be individually toggled by tappingor selecting the individual face or a series of individual facesdisplayed within the graphical user interface.

A story table 312 stores data regarding collections of messages andassociated image, video, or audio data, which are compiled into acollection (e.g., a story or a gallery). The creation of a particularcollection may be initiated by a particular user (e.g., each user forwhich a record is maintained in the entity table 308). A user may createa “personal story” in the form of a collection of content that has beencreated and sent/broadcast by that user. To this end, the user interfaceof the messaging client 104 may include an icon that is user-selectableto enable a sending user to add specific content to his or her personalstory.

A collection may also constitute a “live story,” which is a collectionof content from multiple users that is created manually, automatically,or using a combination of manual and automatic techniques. For example,a “live story” may constitute a curated stream of user-submitted contentfrom varies locations and events. Users whose client devices havelocation services enabled and are at a common location event at aparticular time may, for example, be presented with an option, via auser interface of the messaging client 104, to contribute content to aparticular live story. The live story may be identified to the user bythe messaging client 104, based on his or her location. The end resultis a “live story” told from a community perspective.

A further type of content collection is known as a “location story,”which enables a user whose client device 102 is located within aspecific geographic location (e.g., on a college or university campus)to contribute to a particular collection. In some examples, acontribution to a location story may require a second degree ofauthentication to verify that the end user belongs to a specificorganization or other entity (e.g., is a student on the universitycampus).

A user memory table 318 stores data regarding one or more “usermemories,” where each user memory corresponds to content (e.g., images,videos and/or audio files) saved by an individual user for subsequentaccess by that user. The creation and saving of a particular user memorymay be initiated by the individual user (e.g., each user for which arecord is maintained in the entity table 308). Moreover, each usermemory stored within the user memory table 318 may be viewed, editedand/or sent by the individual user.

For example, if a user creates content (e.g., for exchanging with othersin messaging), the created content, by default, may typically beautomatically deleted and removed from storage after a specified timeperiod (e.g., one hour, one minute, one second, etc.). However, if priorto the specified time period when the content is automatically deleted,the user selects the content for permanent retention (e.g., via a “save”interface), the content may be added as a user memory in the user memorytable 318. The saved content may be accessible by the individual userfor viewing, editing and/or sharing with other users.

As mentioned above, the video table 314 stores video data that, in oneexample, is associated with messages for which records are maintainedwithin the message table 306. Similarly, the image table 316 storesimage data associated with messages for which message data is stored inthe entity table 308. The entity table 308 may associate variousaugmentations from the augmentation table 310 with various images andvideos stored in the image table 316 and the video table 314.

FIG. 4 is a schematic diagram illustrating a structure of a message 400,according to some examples, generated by a messaging client 104 forcommunication to a further messaging client 104 or the messaging server118. The content of a particular message 400 is used to populate themessage table 306 stored within the database 126, accessible by themessaging server 118. Similarly, the content of a message 400 is storedin memory as “in-transit” or “in-flight” data of the client device 102or the application servers 114. A message 400 is shown to include thefollowing example components:

-   -   message identifier 402: a unique identifier that identifies the        message 400.    -   message text payload 404: text, to be generated by a user via a        user interface of the client device 102, and that is included in        the message 400.    -   message image payload 406: image data, captured by a camera        component of a client device 102 or retrieved from a memory        component of a client device 102, and that is included in the        message 400. Image data for a sent or received message 400 may        be stored in the image table 316.    -   message video payload 408: video data, captured by a camera        component or retrieved from a memory component of the client        device 102, and that is included in the message 400. Video data        for a sent or received message 400 may be stored in the video        table 314.    -   message audio payload 410: audio data, captured by a microphone        or retrieved from a memory component of the client device 102,        and that is included in the message 400.    -   message augmentation data 412: augmentation data (e.g., filters,        stickers, or other annotations or enhancements) that represents        augmentations to be applied to message image payload 406,        message video payload 408, or message audio payload 410 of the        message 400. Augmentation data for a sent or received message        400 may be stored in the augmentation table 310.    -   message duration parameter 414: parameter value indicating, in        seconds, the amount of time for which content of the message        (e.g., the message image payload 406, message video payload 408,        message audio payload 410) is to be presented or made accessible        to a user via the messaging client 104.    -   message geolocation parameter 416: geolocation data (e.g.,        latitudinal and longitudinal coordinates) associated with the        content payload of the message. Multiple message geolocation        parameter 416 values may be included in the payload, each of        these parameter values being associated with respect to content        items included in the content (e.g., a specific image into        within the message image payload 406, or a specific video in the        message video payload 408).    -   message story identifier 418: identifier values identifying one        or more content collections (e.g., “stories” identified in the        story table 312) with which a particular content item in the        message image payload 406 of the message 400 is associated. For        example, multiple images within the message image payload 406        may each be associated with multiple content collections using        identifier values.    -   message tag 420: each message 400 may be tagged with multiple        tags, each of which is indicative of the subject matter of        content included in the message payload. For example, where a        particular image included in the message image payload 406        depicts an animal (e.g., a lion), a tag value may be included        within the message tag 420 that is indicative of the relevant        animal. Tag values may be generated manually, based on user        input, or may be automatically generated using, for example,        image recognition.    -   message sender identifier 422: an identifier (e.g., a messaging        system identifier, email address, or device identifier)        indicative of a user of the Client device 102 on which the        message 400 was generated and from which the message 400 was        sent.    -   message receiver identifier 424: an identifier (e.g., a        messaging system identifier, email address, or device        identifier) indicative of a user of the client device 102 to        which the message 400 is addressed.

The contents (e.g., values) of the various components of message 400 maybe pointers to locations in tables within which content data values arestored. For example, an image value in the message image payload 406 maybe a pointer to (or address of) a location within an image table 316.Similarly, values within the message video payload 408 may point to datastored within a video table 314, values stored within the messageaugmentations 412 may point to data stored in an augmentation table 310,values stored within the message story identifier 418 may point to datastored in a story table 312, and values stored within the message senderidentifier 422 and the message receiver identifier 424 may point to userrecords stored within an entity table 308.

FIG. 5 is a diagram illustrating a user interface arrangement 500configured to capture, preview and edit (e.g., trim) video, inaccordance with some example embodiments. For explanatory purposes, theuser interface arrangement 500 is primarily described herein withreference to the messaging client 104 of FIG. 1 , and the augmentationsystem 208 of FIG. 2 . Not all of the depicted and describedinterfaces/components may be used in all implementations, and one ormore embodiments may include additional or differentinterfaces/components than those shown and described with respect to thefigure. Variations in the arrangement and type of theinterfaces/components may be made without departing from the spirit orscope of the claims as set forth herein.

The user interface arrangement 500 may be implemented at least in partby the augmentation system 208. As noted above, augmentation system 208may correspond to a subsystem of the messaging system 100, and may besupported on the client side by the messaging client 104 and/or on theserver side by the application servers 114. In one or more embodiments,the capturing, previewing and editing of video as described herein maybe implemented client side, server side and/or a combination of clientside and server side.

As shown in FIG. 5 , the capture user interface 502 includes a cameraselection button 506, which is user-selectable for switching between arear-facing camera and a front-facing camera of the client device 102.The capture user interface 502 further includes a flash button 508 foractivating or deactivating a flash with respect to captured image data510 (captured video and/or pictures). In addition, the capture userinterface 502 includes a capture button 512 which is user-selectable tocapture video (e.g., video clips) and/or images (e.g., pictures).

Moreover, the capture user interface 502 includes a carousel launchbutton 514 for launching a carousel interface (not shown) within thecapture user interface 502. In one or more embodiments, the carouselinterface allows the user to cycle through and/or select differentaugmented reality content items (e.g., Lenses) to apply/display withrespect to images (e.g., video) currently being captured by the devicecamera and being displayed on the device screen. Each of the availableaugmented reality content items is represented by an icon which isuser-selectable for switching to the respective augmented realitycontent item.

In one or more embodiments, the messaging client 104 provides for a userto select (e.g., via a selection button provided within the capture userinterface 502) between a first camera mode and a second camera mode forvideo capture. For example, the first camera mode corresponds withcapturing a single video clip which is usable to generate a mediacontent item. As described herein, a “video clip” corresponds to aseries of video frames that runs for an uninterrupted period of time.For example, a video clip corresponds with the video captured frommoment that the camera of starts recording until the moment the camerastops recording.

The second camera mode corresponds with capturing multiple video clipswhich may be combined to generate the media content item. In one or moreembodiments, the messaging client 104 defaults to the first camera mode.For example, upon startup of the messaging client 104, the messagingclient 104 activates the camera of the client device 102 to displaycaptured image data 510 in real time, and to default to the first cameramode with respect to the capture user interface 502.

In the first camera mode, the capture button 512 is selectable tocapture a single video clip via a predefined gesture (e.g., apress-and-hold gesture, where video is recorded for the duration of thehold). In addition, the capture button 512 is selectable to capture apicture via another predefined gesture (e.g., tap gesture).

In the second camera mode, the behavior of the capture button 512 maydiffer from that of the first camera mode in order to facilitatecapturing multiple video clips. In one or more embodiments, the capturebutton 512 is responsive to different types of touch input for capturingvideo clips. In a first example, the capture button 512 is selectable tocapture a video clip via a press-and-hold gesture (e.g., where video isrecorded for the duration of the hold). In another example, the capturebutton 512 is selectable to capture a video clip via first and secondtap gestures, with the first tap gesture initiating video capture andthe second tap gesture ending video capture for the video clip (e.g.,corresponding to hands-free recording).

In one or more embodiments, the messaging client 104 provides forswitching from the capture user interface 502 to the preview userinterface 504 upon completion of video capture. With respect to thefirst camera mode, video capture may automatically complete uponcapturing the single video clip (e.g., upon release of the correspondingpress-and-hold gesture). Regarding the second camera mode, video capturemay complete upon user selection of a preview button (not shown), whichis a selectable button within the capture user interface 502 fordirecting to the preview user interface 504.

The preview user interface 504 provides for previewing and/or editingcaptured video. In addition, the preview user interface 504 providesuser-selectable elements for generating the media content item based onthe captured video. The preview user interface 504 includes editingtools 516 for modifying/annotating (e.g., drawing on, adding text to,adding stickers to, cropping, and the like) the captured video. Theediting tools 516 may include playback options 518, which providedifferent options for playback (e.g., with respect to a viewing user) ofthe generated media content item. For example, the playback options 518include looping, bouncing (e.g., switching between forward and reverseplayback) and/or single playback of the media content item.

Moreover, the playback options 518 may include a user-selectable optionto trim the video within the preview user interface 504. For example,the user-selectable option to trim may be presented with a correspondingtip, before presenting the loop, bounce or single playback options.

In one or more embodiments, the preview user interface 504 furtherincludes: a save button 526 which is selectable to save the capturedvideo (e.g., with modifications/annotations) as a media content item(e.g., a user memory within the user memory table 318); a story button528 which is selectable to create or update a Story based on thecaptured video (e.g., with modifications/annotations); and a send button530 which is user selectable to send a media content item which includesthe captured video (e.g., with modifications/annotations) to acontact/friend and/or to broadcast the media content item in associationwith a feed interface (e.g., for viewing by other users who are notnecessarily contacts/friends). The preview user interface 504 furtherincludes an audio button 524 which is selectable to modify audiosignal(s) associated with the captured video.

In one or more embodiments, the preview region 522 provides for loopingplayback (e.g., for preview purposes) of the captured video withmodifications/annotations. In addition, the messaging client 104 (e.g.,in conjunction with the messaging server system 108) is configured togenerate a media content item based on the captured video andcorresponding modifications/annotations (e.g., edits such as trimming).

While the example of FIG. 5 relates to displaying the preview userinterface 504 based on recent video captured via the capture userinterface 502, it is possible for the preview user interface 504 to besurfaced based on previously-stored video(s). For example, the capturedvideo may correspond to a video stored in the video table 314. The videomay correspond to one or more of a user memory (e.g., associated withthe user memory table 318), a message (e.g., associated with the messagetable 306), or a content collection (e.g., a Story, in association withthe story table 312). Thus, the edit operations (e.g., trimming,splitting) described below with respect to FIGS. 6A-6C may apply torecent video captured via the capture user interface 502, or topreviously-stored video(s).

FIGS. 6A-6C illustrate a user interface (e.g., the preview userinterface 602) for trimming captured video to generate a media contentitem, in accordance with some example embodiments. FIGS. 6A-6C depictexample scenarios in which a preview bar 604 is in a contracted state(FIG. 6A), the preview bar 604 is in an expanded state (FIG. 6B), andthe user split the captured video into several video clips via thepreview bar 604 (FIG. 6C).

Similar to the preview user interface 504 of FIG. 5 , the preview userinterfaces 602 may include one or more of the following interfaceelements: a save button 610 for saving the video clips with anyassociated edits as a media content item; a story button 612 forcreating a Story based on the video clips and any associated edits; asend button 614 for sending and/or broadcasting the media content item;editing tools (not shown) for modifying/annotating the captured videoclips, including playback options for either looping, bouncing or singleplayback of the resulting media content item; a close button (not shown)for exiting the preview user interface 602, for example, withoutpreserving captured video and/or edits; and/or a preview region (notshown) for looping playback of the captured video clips. These interfaceelements in the preview user interfaces 602 of FIGS. 6A-6C areconfigured to perform functions similar to those described above withrespect to the preview user interface 504 of FIG. 5 .

As shown in the example of FIG. 6A, the preview user interface 602includes a preview bar 604. In one or more embodiments, the preview bar604 is always displayed when switching from the capture user interface(e.g., see capture user interface 502 in FIG. 5 ) to the preview userinterface 602. Alternatively, the messaging client 104 may be configuredto display the preview bar 604 when the length of the captured videoexceeds a preset length (e.g., 12 seconds), but to otherwise not displaythe preview bar 604.

The preview bar 604 includes a first set of thumbnails selected torepresent the captured video. For example, the messaging client 104 mayimplement or otherwise access a thumbnail selection algorithm forselecting a preset number of video frames, within the captured video,that are representative of the captured video. In addition, a positionindicator 606 indicates a current playback position (e.g., within thethumbnails) for the looped playback within the preview region. Withrespect to the editing tools (not shown), edits such as drawing on,adding text to, adding stickers to and/or cropping are applied withrespect to the captured video as a whole.

In one or more embodiments, the preview bar 604 is user-selectable toactivate an interface to trim the captured video. For example, thepreview user interface 602 may present a tool tip (“trim your mediacontent item”) to select the preview bar 604 for trimming. The tool tipmay be displayed only once (e.g., a first time), to advise the userabout the option to trim.

Alternatively or in addition, the playback options interface (e.g., seeplayback options 518 of FIG. 5 ) includes a user-selectable option totrim the captured video. As noted above, the playback options interfaceis selectable to loop, bounce or playback the video a single time. Asdescribed herein, the playback options interface further includes anoption to activate an interface to trim. For example, the option to trimis presented, via the playback options interface, before presenting theloop, bounce or single playback options. In one or more embodiments, theoption to trim is presented with a tool tip (e.g., displayed a firsttime only upon user selection of the playback options interface) or withother text indicating a trim operation, and/or with an icon indicatingthe trim operation.

In response to user input selecting to trim (e.g., via the playbackoptions interface or selection of the preview bar 604), the messagingclient 104 provides for updating the preview user interface 602 as shownin FIG. 6B. In the example of FIG. 6B, the messaging client 104continues providing the looped playback. However, the messaging client104 provides for updating the preview bar 604 to include a front handle616 and a back handle 618. In one or more embodiments, the user mayperform a tap gesture within the looped playback area (e.g., see previewregion 522 of FIG. 5 ) to return to the preview user interface 602presented with respect to FIG. 6A (e.g., with no front and backhandles).

Regarding FIG. 6B, the front handle 616 is selectable to perform a trimoperation for taking off (e.g., or adding back) with respect to thebeginning of the captured video. For example, the user may drag thefront handle 616 to a desired trim position, at which point the user mayrelease the drag gesture to effect the trim. During the drag, the loopedplayback (e.g., see the preview region 522 shown in FIG. 5 ) may bereplaced in real-time to display the frame(s) corresponding to thecurrent position(s) of the drag. In this manner, the user may also usethe front handle 616 to scrub through (e.g., navigate through) thecaptured video. In one or more embodiments, upon release of the drag,the looped playback may resume.

In a similar manner, the back handle 618 is selectable to perform a trimoperation for taking off (e.g., or adding back) with respect to the endof the captured video, and/or to scrub through the frames thereof. Thelooped playback may display frames in real-time based on the positionsof the back handle 618.

In the example of FIG. 6B, the preview bar 604 may be populated withthumbnails (e.g., representative frames) in addition to those providedwith respect to FIG. 6A. In this regard, FIG. 6A may correspond to acontracted state of the preview bar 604, while FIG. 6B may correspond toan expanded state of the preview bar 604. In one or more embodiments,frames within the preview bar 604 may be added or subtracted in adynamic manner in response to trimming and/or scrubbing operation(s)performed by the user via the front handle 616 and/or the back handle618.

The messaging client 104 may further provide for splitting the capturedvideo via a scissors icon 620. For example, the scissors icon 620 ispresented in association with the position indicator 606, whichindicates the current playback position with respect to the loopedplayback within the preview region. In the example of FIG. 6B, thescissors icon 620 and/or the position indicator 606 is moveable (e.g.,via a drag gesture) among the video frames of the preview bar 604.During the drag gesture, the preview region may depict videocorresponding to the current position of the position indicator 606 asbeing dragged by the user (e.g., and return to looped playback uponcompletion of the drag gesture).

In one or more embodiments, the messaging client 104 provides for thescissors icon 620 to appear for a preset time (e.g., 1 second) uponswitching the preview user interface 602 from the contracted state ofFIG. 6A to the expanded state of FIG. 6B. After the preset time, thescissors icon 620 is configured to fade out, and to reappear when theuser drags the position indicator 606 in order to perform a splitoperation.

A tool tip displayed in association with the scissors icon 620 mayindicate a predefined gesture (e.g., an upward swipe gesture) forcausing the captured video to be split. In response to the predefinedgesture, the messaging client 104 provides for splitting the capturedvideo into separate video clips at the current position of the positionindicator 606 as dragged by the user. In one or more embodiments,splitting the video into separate video clips provides for the user toperform trim and/or edit operations with respect to each of the separatevideo clips.

FIG. 6C illustrates an example scenario in which the user performedmultiple split operations via the scissors icon 620 in conjunction withthe position indicator 606. In the example of FIG. 6C, the capturedvideo has been split into four separate video clips. Each video clip ispresented as a separate block within the preview bar 604.

The messaging client 104 may continue providing the looped playback(e.g., within the preview region 522 of FIG. 5 ) in association with aposition indicator 624. In response to user selection of a particularblock (e.g., a selected block 622), the messaging client 104 updates theselected block 622 to include a front handle 626, a back handle 628, ascissors icon 630 and a delete button 632. Each of the front handle 626and the back handle 628 is selectable to perform a trim operation fortaking off (e.g., or adding back) with respect to the individual clip ofthe selected blocks 622, and/or to scrub through the frames thereof. Thelooped playback may display frames in real-time based on the positionsof the front handle 626 and/or the back handle 628.

In the example of FIG. 6C, the preview bar 604 may be populated withadditional frames (e.g., relative to those presented in FIG. 6B) for theselected block 622. In one or more embodiments, frames of the selectedblock 622 may be added or subtracted in a dynamic manner in response totrimming and/or scrubbing operation(s) performed by the user via thefront handle 626 and/or the back handle 628.

The scissors icon 630 in association with the position indicator 624 isselectable for splitting the selected block 622 based on a drag gestureand an upward swipe gesture as described above. The delete button 632 isselectable for deleting the video clip corresponding to the selectedblock 622. It is noted that the user may select one or more blockswithin the preview bar 604, for trimming, scrubbing, splitting and/ordeleting as described.

In one or more embodiments, the editing tools (e.g., see editing tools516 of FIG. 5 ) provide for modifying/annotating the captured video. Forexample, the editing tools are user-selectable for drawing on, addingtext to, adding stickers to, cropping, and the like with respect to theentirety of the captured video and/or the separate video clips, forgenerating the media content item.

In one or more embodiments, the messaging client 104 may facilitatestoring the video clips as modified by trimming, splitting, editingand/or deletion in local memory (e.g., in association with thecollection management system 204 and/or the augmentation system 208). Assuch, it is possible to preserve such modifications with respect toswitching between user interfaces, switching between other applications,and the like.

FIG. 7 is a flowchart illustrating a process 700 for trimming videowithin a messaging system, in accordance with some example embodiments.For explanatory purposes, the process 700 is primarily described hereinwith reference to the messaging client 104 of FIG. 1 . However, one ormore blocks (or operations) of the process 700 may be performed by oneor more other components, and/or by other suitable devices. Further forexplanatory purposes, the blocks (or operations) of the process 700 aredescribed herein as occurring in serial, or linearly. However, multipleblocks (or operations) of the process 700 may occur in parallel orconcurrently. In addition, the blocks (or operations) of the process 700need not be performed in the order shown and/or one or more blocks (oroperations) of the process 700 need not be performed and/or can bereplaced by other operations. The process 700 may be terminated when itsoperations are completed. In addition, the process 700 may correspond toa method, a procedure, an algorithm, etc.

The messaging client 104 provides a capture user interface for capturinga video to generate a media content item (block 702). The messagingclient 104 displays, upon completion of capturing the video, a previewuser interface for previewing and editing the captured video in order togenerate the media content item, the preview user interface including aninterface element for selecting to trim the captured video or to set aplayback option for the media content item (block 704).

The playback option may correspond to one of looping the captured video,bouncing the captured video or playing back the captured video a singletime. The messaging client 104 receives, via the interface element, userinput selecting to trim the captured video (block 706).

The messaging client 104 displays, in response to the receiving, apreview bar within the preview user interface, the preview bar includinga set of frames of the captured video and further including a fronthandle and a back handle respectively positioned in front and in back ofthe set of frames, each of the front handle and the back handle beingselectable to trim the captured video (block 708). The front and backhandles may be selectable to scrub through the captured video.

Displaying the preview bar with the front and back handles and with theset of frames may correspond to an expanded state of the preview bar.Prior to the receiving, the preview bar may be displayed in a contractedstate without the front and back handles and with a subset of the set offrames, the preview bar in the contracted state being user-selectable toswitch to the expanded state. The preview bar may be automaticallydisplayed in the contracted state in a case where a length of thecaptured video exceeds a preset length.

The preview bar may further include a splitting element which isuser-selectable to split the captured video into separate video clips.Each video clip of the separate video clips may be presented with atleast one of respective front and back handles for trimming the videoclip, a respective splitting element for splitting the video clip, and arespective delete button for deleting the video clip.

The preview user interface may further include a playback region forlooping playback the captured video. The playback region may be userselectable to remove the preview bar from display within the previewuser interface.

FIG. 8 is a schematic diagram illustrating an access-limiting process1000, in terms of which access to content (e.g., an ephemeral message802, and associated multimedia payload of data) or a content collection(e.g., an ephemeral message group 804) may be time-limited (e.g., madeephemeral).

An ephemeral message 802 is shown to be associated with a messageduration parameter 806, the value of which determines an amount of timethat the ephemeral message 802 will be displayed to a receiving user ofthe ephemeral message 802 by the messaging client 104. In one example,an ephemeral message 802 is viewable by a receiving user for up to amaximum of 10 seconds, depending on the amount of time that the sendinguser specifies using the message duration parameter 806.

The message duration parameter 806 and the message receiver identifier424 are shown to be inputs to a message timer 810, which is responsiblefor determining the amount of time that the ephemeral message 802 isshown to a particular receiving user identified by the message receiveridentifier 424. In particular, the ephemeral message 802 will only beshown to the relevant receiving user for a time period determined by thevalue of the message duration parameter 806. The message timer 810 isshown to provide output to a more generalized ephemeral timer system202, which is responsible for the overall timing of display of content(e.g., an ephemeral message 802) to a receiving user.

The ephemeral message 802 is shown in FIG. 8 to be included within anephemeral message group 804 (e.g., a collection of messages in apersonal story, or an event story). The ephemeral message group 804 hasan associated group duration parameter 808, a value of which determinesa time duration for which the ephemeral message group 804 is presentedand accessible to users of the messaging system 100. The group durationparameter 808, for example, may be the duration of a music concert,where the ephemeral message group 804 is a collection of contentpertaining to that concert. Alternatively, a user (either the owninguser or a curator user) may specify the value for the group durationparameter 808 when performing the setup and creation of the ephemeralmessage group 804.

Additionally, each ephemeral message 802 within the ephemeral messagegroup 804 has an associated group participation parameter 812, a valueof which determines the duration of time for which the ephemeral message802 will be accessible within the context of the ephemeral message group804. Accordingly, a particular ephemeral message group 804 may “expire”and become inaccessible within the context of the ephemeral messagegroup 804, prior to the ephemeral message group 804 itself expiring interms of the group duration parameter 808. The group duration parameter808, group participation parameter 812, and message receiver identifier424 each provide input to a group timer 814, which operationallydetermines, firstly, whether a particular ephemeral message 802 of theephemeral message group 804 will be displayed to a particular receivinguser and, if so, for how long. Note that the ephemeral message group 804is also aware of the identity of the particular receiving user as aresult of the message receiver identifier 424.

Accordingly, the group timer 814 operationally controls the overalllifespan of an associated ephemeral message group 804, as well as anindividual ephemeral message 802 included in the ephemeral message group804. In one example, each and every ephemeral message 802 within theephemeral message group 804 remains viewable and accessible for a timeperiod specified by the group duration parameter 808. In a furtherexample, a certain ephemeral message 802 may expire, within the contextof ephemeral message group 804, based on a group participation parameter812. Note that a message duration parameter 806 may still determine theduration of time for which a particular ephemeral message 802 isdisplayed to a receiving user, even within the context of the ephemeralmessage group 804. Accordingly, the message duration parameter 806determines the duration of time that a particular ephemeral message 802is displayed to a receiving user, regardless of whether the receivinguser is viewing that ephemeral message 802 inside or outside the contextof an ephemeral message group 804.

The ephemeral timer system 202 may furthermore operationally remove aparticular ephemeral message 802 from the ephemeral message group 804based on a determination that it has exceeded an associated groupparticipation parameter 812. For example, when a sending user hasestablished a group participation parameter 812 of 24 hours fromposting, the ephemeral timer system 202 will remove the relevantephemeral message 802 from the ephemeral message group 804 after thespecified 24 hours. The ephemeral timer system 202 also operates toremove an ephemeral message group 804 when either the groupparticipation parameter 812 for each and every ephemeral message 802within the ephemeral message group 804 has expired, or when theephemeral message group 804 itself has expired in terms of the groupduration parameter 808.

In certain use cases, a creator of a particular ephemeral message group804 may specify an indefinite group duration parameter 808. In thiscase, the expiration of the group participation parameter 812 for thelast remaining ephemeral message 802 within the ephemeral message group804 will determine when the ephemeral message group 804 itself expires.In this case, a new ephemeral message 802, added to the ephemeralmessage group 804, with a new group participation parameter 812,effectively extends the life of an ephemeral message group 804 to equalthe value of the group participation parameter 812.

Responsive to the ephemeral timer system 202 determining that anephemeral message group 804 has expired (e.g., is no longer accessible),the ephemeral timer system 202 communicates with the messaging system100 (and, for example, specifically the messaging client 104) to causean indicium (e.g., an icon) associated with the relevant ephemeralmessage group 804 to no longer be displayed within a user interface ofthe messaging client 104. Similarly, when the ephemeral timer system 202determines that the message duration parameter 806 for a particularephemeral message 802 has expired, the ephemeral timer system 202 causesthe messaging client 104 to no longer display an indicium (e.g., an iconor textual identification) associated with the ephemeral message 802.

FIG. 9 is a diagrammatic representation of the machine 900 within whichinstructions 910 (e.g., software, a program, an application, an applet,an app, or other executable code) for causing the machine 900 to performany one or more of the methodologies discussed herein may be executed.For example, the instructions 910 may cause the machine 900 to executeany one or more of the methods described herein. The instructions 910transform the general, non-programmed machine 900 into a particularmachine 900 programmed to carry out the described and illustratedfunctions in the manner described. The machine 900 may operate as astandalone device or may be coupled (e.g., networked) to other machines.In a networked deployment, the machine 900 may operate in the capacityof a server machine or a client machine in a server-client networkenvironment, or as a peer machine in a peer-to-peer (or distributed)network environment. The machine 900 may comprise, but not be limitedto, a server computer, a client computer, a personal computer (PC), atablet computer, a laptop computer, a netbook, a set-top box (STB), apersonal digital assistant (PDA), an entertainment media system, acellular telephone, a smartphone, a mobile device, a wearable device(e.g., a smartwatch), a smart home device (e.g., a smart appliance),other smart devices, a web appliance, a network router, a networkswitch, a network bridge, or any machine capable of executing theinstructions 910, sequentially or otherwise, that specify actions to betaken by the machine 900. Further, while only a single machine 900 isillustrated, the term “machine” shall also be taken to include acollection of machines that individually or jointly execute theinstructions 910 to perform any one or more of the methodologiesdiscussed herein. The machine 900, for example, may comprise the clientdevice 102 or any one of a number of server devices forming part of themessaging server system 108. In some examples, the machine 900 may alsocomprise both client and server systems, with certain operations of aparticular method or algorithm being performed on the server-side andwith certain operations of the particular method or algorithm beingperformed on the client-side.

The machine 900 may include processors 904, memory 906, and input/outputI/O components 902, which may be configured to communicate with eachother via a bus 940. In an example, the processors 904 (e.g., a CentralProcessing Unit (CPU), a Reduced Instruction Set Computing (RISC)Processor, a Complex Instruction Set Computing (CISC) Processor, aGraphics Processing Unit (GPU), a Digital Signal Processor (DSP), anApplication Specific Integrated Circuit (ASIC), a Radio-FrequencyIntegrated Circuit (RFIC), another processor, or any suitablecombination thereof) may include, for example, a processor 908 and aprocessor 912 that execute the instructions 910. The term “processor” isintended to include multi-core processors that may comprise two or moreindependent processors (sometimes referred to as “cores”) that mayexecute instructions contemporaneously. Although FIG. 9 shows multipleprocessors 904, the machine 900 may include a single processor with asingle-core, a single processor with multiple cores (e.g., a multi-coreprocessor), multiple processors with a single core, multiple processorswith multiples cores, or any combination thereof.

The memory 906 includes a main memory 914, a static memory 916, and astorage unit 918, both accessible to the processors 904 via the bus 940.The main memory 906, the static memory 916, and storage unit 918 storethe instructions 910 embodying any one or more of the methodologies orfunctions described herein. The instructions 910 may also reside,completely or partially, within the main memory 914, within the staticmemory 916, within machine-readable medium 920 within the storage unit918, within at least one of the processors 904 (e.g., within theProcessor's cache memory), or any suitable combination thereof, duringexecution thereof by the machine 900.

The I/O components 902 may include a wide variety of components toreceive input, provide output, produce output, transmit information,exchange information, capture measurements, and so on. The specific I/Ocomponents 902 that are included in a particular machine will depend onthe type of machine. For example, portable machines such as mobilephones may include a touch input device or other such input mechanisms,while a headless server machine will likely not include such a touchinput device. It will be appreciated that the I/O components 902 mayinclude many other components that are not shown in FIG. 9 . In variousexamples, the I/O components 902 may include user output components 926and user input components 928. The user output components 926 mayinclude visual components (e.g., a display such as a plasma displaypanel (PDP), a light-emitting diode (LED) display, a liquid crystaldisplay (LCD), a projector, or a cathode ray tube (CRT)), acousticcomponents (e.g., speakers), haptic components (e.g., a vibratory motor,resistance mechanisms), other signal generators, and so forth. The userinput components 928 may include alphanumeric input components (e.g., akeyboard, a touch screen configured to receive alphanumeric input, aphoto-optical keyboard, or other alphanumeric input components),point-based input components (e.g., a mouse, a touchpad, a trackball, ajoystick, a motion sensor, or another pointing instrument), tactileinput components (e.g., a physical button, a touch screen that provideslocation and force of touches or touch gestures, or other tactile inputcomponents), audio input components (e.g., a microphone), and the like.

In further examples, the I/O components 902 may include biometriccomponents 930, motion components 932, environmental components 934, orposition components 936, among a wide array of other components. Forexample, the biometric components 930 include components to detectexpressions (e.g., hand expressions, facial expressions, vocalexpressions, body gestures, or eye-tracking), measure biosignals (e.g.,blood pressure, heart rate, body temperature, perspiration, or brainwaves), identify a person (e.g., voice identification, retinalidentification, facial identification, fingerprint identification, orelectroencephalogram-based identification), and the like. The motioncomponents 932 include acceleration sensor components (e.g.,accelerometer), gravitation sensor components, rotation sensorcomponents (e.g., gyroscope).

The environmental components 934 include, for example, one or cameras(with still image/photograph and video capabilities), illuminationsensor components (e.g., photometer), temperature sensor components(e.g., one or more thermometers that detect ambient temperature),humidity sensor components, pressure sensor components (e.g.,barometer), acoustic sensor components (e.g., one or more microphonesthat detect background noise), proximity sensor components (e.g.,infrared sensors that detect nearby objects), gas sensors (e.g., gasdetection sensors to detection concentrations of hazardous gases forsafety or to measure pollutants in the atmosphere), or other componentsthat may provide indications, measurements, or signals corresponding toa surrounding physical environment.

With respect to cameras, the client device 102 may have a camera systemcomprising, for example, front cameras on a front surface of the clientdevice 102 and rear cameras on a rear surface of the client device 102.The front cameras may, for example, be used to capture still images andvideo of a user of the client device 102 (e.g., “selfies”), which maythen be augmented with augmentation data (e.g., filters) describedabove. The rear cameras may, for example, be used to capture stillimages and videos in a more traditional camera mode, with these imagessimilarly being augmented with augmentation data. In addition to frontand rear cameras, the client device 102 may also include a 360° camerafor capturing 360° photographs and videos.

Further, the camera system of a client device 102 may include dual rearcameras (e.g., a primary camera as well as a depth-sensing camera), oreven triple, quad or penta rear camera configurations on the front andrear sides of the client device 102. These multiple cameras systems mayinclude a wide camera, an ultra-wide camera, a telephoto camera, a macrocamera and a depth sensor, for example.

The position components 936 include location sensor components (e.g., aGPS receiver component), altitude sensor components (e.g., altimeters orbarometers that detect air pressure from which altitude may be derived),orientation sensor components (e.g., magnetometers), and the like.

Communication may be implemented using a wide variety of technologies.The I/O components 902 further include communication components 938operable to couple the machine 900 to a network 922 or devices 924 viarespective coupling or connections. For example, the communicationcomponents 938 may include a network interface Component or anothersuitable device to interface with the network 922. In further examples,the communication components 938 may include wired communicationcomponents, wireless communication components, cellular communicationcomponents, Near Field Communication (NFC) components, Bluetooth®components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and othercommunication components to provide communication via other modalities.The devices 924 may be another machine or any of a wide variety ofperipheral devices (e.g., a peripheral device coupled via a USB).

Moreover, the communication components 938 may detect identifiers orinclude components operable to detect identifiers. For example, thecommunication components 938 may include Radio Frequency Identification(RFID) tag reader components, NFC smart tag detection components,optical reader components (e.g., an optical sensor to detectone-dimensional bar codes such as Universal Product Code (UPC) bar code,multi-dimensional bar codes such as Quick Response (QR) code, Azteccode, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2Dbar code, and other optical codes), or acoustic detection components(e.g., microphones to identify tagged audio signals). In addition, avariety of information may be derived via the communication components938, such as location via Internet Protocol (IP) geolocation, locationvia Wi-Fi® signal triangulation, location via detecting an NFC beaconsignal that may indicate a particular location, and so forth.

The various memories (e.g., main memory 914, static memory 916, andmemory of the processors 904) and storage unit 918 may store one or moresets of instructions and data structures (e.g., software) embodying orused by any one or more of the methodologies or functions describedherein. These instructions (e.g., the instructions 910), when executedby processors 904, cause various operations to implement the disclosedexamples.

The instructions 910 may be transmitted or received over the network922, using a transmission medium, via a network interface device (e.g.,a network interface component included in the communication components938) and using any one of several well-known transfer protocols (e.g.,hypertext transfer protocol (HTTP)). Similarly, the instructions 910 maybe transmitted or received using a transmission medium via a coupling(e.g., a peer-to-peer coupling) to the devices 924.

FIG. 10 is a block diagram 1000 illustrating a software architecture1004, which can be installed on any one or more of the devices describedherein. The software architecture 1004 is supported by hardware such asa machine 1002 that includes processors 1020, memory 1026, and I/Ocomponents 1038. In this example, the software architecture 1004 can beconceptualized as a stack of layers, where each layer provides aparticular functionality. The software architecture 1004 includes layerssuch as an operating system 1012, libraries 1010, frameworks 1008, andapplications 1006. Operationally, the applications 1006 invoke API calls1050 through the software stack and receive messages 1052 in response tothe API calls 1050.

The operating system 1012 manages hardware resources and provides commonservices. The operating system 1012 includes, for example, a kernel1014, services 1016, and drivers 1022. The kernel 1014 acts as anabstraction layer between the hardware and the other software layers.For example, the kernel 1014 provides memory management, processormanagement (e.g., scheduling), component management, networking, andsecurity settings, among other functionality. The services 1016 canprovide other common services for the other software layers. The drivers1022 are responsible for controlling or interfacing with the underlyinghardware. For instance, the drivers 1022 can include display drivers,camera drivers, BLUETOOTH® or BLUETOOTH® Low Energy drivers, flashmemory drivers, serial communication drivers (e.g., USB drivers), WI-FI®drivers, audio drivers, power management drivers, and so forth.

The libraries 1010 provide a common low-level infrastructure used by theapplications 1006. The libraries 1010 can include system libraries 1018(e.g., C standard library) that provide functions such as memoryallocation functions, string manipulation functions, mathematicfunctions, and the like. In addition, the libraries 1010 can include APIlibraries 1024 such as media libraries (e.g., libraries to supportpresentation and manipulation of various media formats such as MovingPicture Experts Group-4 (MPEG4), Advanced Video Coding (H.264 or AVC),Moving Picture Experts Group Layer-3 (MP3), Advanced Audio Coding (AAC),Adaptive Multi-Rate (AMR) audio codec, Joint Photographic Experts Group(JPEG or JPG), or Portable Network Graphics (PNG)), graphics libraries(e.g., an OpenGL framework used to render in two dimensions (2D) andthree dimensions (3D) in a graphic content on a display), databaselibraries (e.g., SQLite to provide various relational databasefunctions), web libraries (e.g., WebKit to provide web browsingfunctionality), and the like. The libraries 1010 can also include a widevariety of other libraries 1028 to provide many other APIs to theapplications 1006.

The frameworks 1008 provide a common high-level infrastructure that isused by the applications 1006. For example, the frameworks 1008 providevarious graphical user interface (GUI) functions, high-level resourcemanagement, and high-level location services. The frameworks 1008 canprovide a broad spectrum of other APIs that can be used by theapplications 1006, some of which may be specific to a particularoperating system or platform.

In an example, the applications 1006 may include a home application1036, a contacts application 1030, a browser application 1032, a bookreader application 1034, a location application 1042, a mediaapplication 1044, a messaging application 1046, a game application 1048,and a broad assortment of other applications such as a third-partyapplication 1040. The applications 1006 are programs that executefunctions defined in the programs. Various programming languages can beemployed to create one or more of the applications 1006, structured in avariety of manners, such as object-oriented programming languages (e.g.,Objective-C, Java, or C++) or procedural programming languages (e.g., Cor assembly language). In a specific example, the third-partyapplication 1040 (e.g., an application developed using the ANDROID™ orIOS™ software development kit (SDK) by an entity other than the vendorof the particular platform) may be mobile software running on a mobileoperating system such as IOS™, ANDROID™, WINDOWS® Phone, or anothermobile operating system. In this example, the third-party application1040 can invoke the API calls 1050 provided by the operating system 1012to facilitate functionality described herein.

Glossary

“Carrier signal” refers to any intangible medium that is capable ofstoring, encoding, or carrying instructions for execution by themachine, and includes digital or analog communications signals or otherintangible media to facilitate communication of such instructions.Instructions may be transmitted or received over a network using atransmission medium via a network interface device.

“Client device” refers to any machine that interfaces to acommunications network to obtain resources from one or more serversystems or other client devices. A client device may be, but is notlimited to, a mobile phone, desktop computer, laptop, portable digitalassistants (PDAs), smartphones, tablets, ultrabooks, netbooks, laptops,multi-processor systems, microprocessor-based or programmable consumerelectronics, game consoles, set-top boxes, or any other communicationdevice that a user may use to access a network.

“Communication network” refers to one or more portions of a network thatmay be an ad hoc network, an intranet, an extranet, a virtual privatenetwork (VPN), a local area network (LAN), a wireless LAN (WLAN), a widearea network (WAN), a wireless WAN (WWAN), a metropolitan area network(MAN), the Internet, a portion of the Internet, a portion of the PublicSwitched Telephone Network (PSTN), a plain old telephone service (POTS)network, a cellular telephone network, a wireless network, a Wi-Fi®network, another type of network, or a combination of two or more suchnetworks. For example, a network or a portion of a network may include awireless or cellular network and the coupling may be a Code DivisionMultiple Access (CDMA) connection, a Global System for Mobilecommunications (GSM) connection, or other types of cellular or wirelesscoupling. In this example, the coupling may implement any of a varietyof types of data transfer technology, such as Single Carrier RadioTransmission Technology (1×RTT), Evolution-Data Optimized (EVDO)technology, General Packet Radio Service (GPRS) technology, EnhancedData rates for GSM Evolution (EDGE) technology, third GenerationPartnership Project (3GPP) including 3G, fourth generation wireless (4G)networks, Universal Mobile Telecommunications System (UMTS), High SpeedPacket Access (HSPA), Worldwide Interoperability for Microwave Access(WiMAX), Long Term Evolution (LTE) standard, others defined by variousstandard-setting organizations, other long-range protocols, or otherdata transfer technology.

“Component” refers to a device, physical entity, or logic havingboundaries defined by function or subroutine calls, branch points, APIs,or other technologies that provide for the partitioning ormodularization of particular processing or control functions. Componentsmay be combined via their interfaces with other components to carry outa machine process. A component may be a packaged functional hardwareunit designed for use with other components and a part of a program thatusually performs a particular function of related functions. Componentsmay constitute either software components (e.g., code embodied on amachine-readable medium) or hardware components. A “hardware component”is a tangible unit capable of performing certain operations and may beconfigured or arranged in a certain physical manner. In variousexamples, one or more computer systems (e.g., a standalone computersystem, a client computer system, or a server computer system) or one ormore hardware components of a computer system (e.g., a processor or agroup of processors) may be configured by software (e.g., an applicationor application portion) as a hardware component that operates to performcertain operations as described herein. A hardware component may also beimplemented mechanically, electronically, or any suitable combinationthereof. For example, a hardware component may include dedicatedcircuitry or logic that is permanently configured to perform certainoperations. A hardware component may be a special-purpose processor,such as a field-programmable gate array (FPGA) or an applicationspecific integrated circuit (ASIC). A hardware component may alsoinclude programmable logic or circuitry that is temporarily configuredby software to perform certain operations. For example, a hardwarecomponent may include software executed by a general-purpose processoror other programmable processor. Once configured by such software,hardware components become specific machines (or specific components ofa machine) uniquely tailored to perform the configured functions and areno longer general-purpose processors. It will be appreciated that thedecision to implement a hardware component mechanically, in dedicatedand permanently configured circuitry, or in temporarily configuredcircuitry (e.g., configured by software), may be driven by cost and timeconsiderations. Accordingly, the phrase “hardware component” (or“hardware-implemented component”) should be understood to encompass atangible entity, be that an entity that is physically constructed,permanently configured (e.g., hardwired), or temporarily configured(e.g., programmed) to operate in a certain manner or to perform certainoperations described herein. Considering examples in which hardwarecomponents are temporarily configured (e.g., programmed), each of thehardware components need not be configured or instantiated at any oneinstance in time. For example, where a hardware component comprises ageneral-purpose processor configured by software to become aspecial-purpose processor, the general-purpose processor may beconfigured as respectively different special-purpose processors (e.g.,comprising different hardware components) at different times. Softwareaccordingly configures a particular processor or processors, forexample, to constitute a particular hardware component at one instanceof time and to constitute a different hardware component at a differentinstance of time. Hardware components can provide information to, andreceive information from, other hardware components. Accordingly, thedescribed hardware components may be regarded as being communicativelycoupled. Where multiple hardware components exist contemporaneously,communications may be achieved through signal transmission (e.g., overappropriate circuits and buses) between or among two or more of thehardware components. In examples in which multiple hardware componentsare configured or instantiated at different times, communicationsbetween such hardware components may be achieved, for example, throughthe storage and retrieval of information in memory structures to whichthe multiple hardware components have access. For example, one hardwarecomponent may perform an operation and store the output of thatoperation in a memory device to which it is communicatively coupled. Afurther hardware component may then, at a later time, access the memorydevice to retrieve and process the stored output. Hardware componentsmay also initiate communications with input or output devices, and canoperate on a resource (e.g., a collection of information). The variousoperations of example methods described herein may be performed, atleast partially, by one or more processors that are temporarilyconfigured (e.g., by software) or permanently configured to perform therelevant operations. Whether temporarily or permanently configured, suchprocessors may constitute processor-implemented components that operateto perform one or more operations or functions described herein. As usedherein, “processor-implemented component” refers to a hardware componentimplemented using one or more processors. Similarly, the methodsdescribed herein may be at least partially processor-implemented, with aparticular processor or processors being an example of hardware. Forexample, at least some of the operations of a method may be performed byone or more processors 1004 or processor-implemented components.Moreover, the one or more processors may also operate to supportperformance of the relevant operations in a “cloud computing”environment or as a “software as a service” (SaaS). For example, atleast some of the operations may be performed by a group of computers(as examples of machines including processors), with these operationsbeing accessible via a network (e.g., the Internet) and via one or moreappropriate interfaces (e.g., an API). The performance of certain of theoperations may be distributed among the processors, not only residingwithin a single machine, but deployed across a number of machines. Insome examples, the processors or processor-implemented components may belocated in a single geographic location (e.g., within a homeenvironment, an office environment, or a server farm). In otherexamples, the processors or processor-implemented components may bedistributed across a number of geographic locations.

“Computer-readable storage medium” refers to both machine-storage mediaand transmission media. Thus, the terms include both storagedevices/media and carrier waves/modulated data signals. The terms“machine-readable medium,” “computer-readable medium” and“device-readable medium” mean the same thing and may be usedinterchangeably in this disclosure.

“Ephemeral message” refers to a message that is accessible for atime-limited duration. An ephemeral message may be a text, an image, avideo and the like. The access time for the ephemeral message may be setby the message sender. Alternatively, the access time may be a defaultsetting or a setting specified by the recipient. Regardless of thesetting technique, the message is transitory.

“Machine storage medium” refers to a single or multiple storage devicesand media (e.g., a centralized or distributed database, and associatedcaches and servers) that store executable instructions, routines anddata. The term shall accordingly be taken to include, but not be limitedto, solid-state memories, and optical and magnetic media, includingmemory internal or external to processors. Specific examples ofmachine-storage media, computer-storage media and device-storage mediainclude non-volatile memory, including by way of example semiconductormemory devices, e.g., erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), FPGA, andflash memory devices; magnetic disks such as internal hard disks andremovable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks Theterms “machine-storage medium,” “device-storage medium,”“computer-storage medium” mean the same thing and may be usedinterchangeably in this disclosure. The terms “machine-storage media,”“computer-storage media,” and “device-storage media” specificallyexclude carrier waves, modulated data signals, and other such media, atleast some of which are covered under the term “signal medium.”

“Non-transitory computer-readable storage medium” refers to a tangiblemedium that is capable of storing, encoding, or carrying theinstructions for execution by a machine.

“Signal medium” refers to any intangible medium that is capable ofstoring, encoding, or carrying the instructions for execution by amachine and includes digital or analog communications signals or otherintangible media to facilitate communication of software or data. Theterm “signal medium” shall be taken to include any form of a modulateddata signal, carrier wave, and so forth. The term “modulated datasignal” means a signal that has one or more of its characteristics setor changed in such a matter as to encode information in the signal. Theterms “transmission medium” and “signal medium” mean the same thing andmay be used interchangeably in this disclosure.

What is claimed is:
 1. A method, comprising: providing, by a messagingapplication running on a device, a capture user interface for capturinga video to generate a media content item; automatically switching, bythe messaging application and upon completion of capturing the video,from the capture user interface to a preview user interface forpreviewing and editing the captured video in order to generate the mediacontent item, the preview user interface including an interface elementto select a playback option, from among plural playback options, for themedia content item, the preview user interface further including apreview bar in a contracted state, the contracted state including afirst set of frames of the captured video and omitting front and backhandles, wherein the preview bar is automatically displayed in thecontracted state based on a length of the captured video exceeding apreset length; receiving, by the messaging application and via theinterface element, user input selecting the preview bar; and updating,by the messaging application and in response to the receiving, thepreview bar from the contracted state to an expanded state, the expandedstate including a second set of frames of the captured video which islarger than the first set of frames, further including a front handleand a back handle respectively positioned in front and in back of thesecond set of frames, each of the front handle and the back handle beingselectable to trim the captured video, and further including a splittingelement which is user-selectable to split the captured video intoseparate video clips.
 2. The method of claim 1, wherein the pluralplayback options comprise looping the captured video, bouncing thecaptured video or playing back the captured video a single time.
 3. Themethod of claim 1, wherein the front and back handles are selectable toscrub through the captured video.
 4. The method of claim 1, wherein eachvideo clip of the separate video clips is presented with at least one ofrespective front and back handles for trimming the video clip, arespective splitting element for splitting the video clip, and arespective delete button for deleting the video clip.
 5. The method ofclaim 1, wherein the preview user interface further includes a playbackregion for looping playback of the captured video, and wherein theplayback region is user selectable to remove the preview bar fromdisplay within the preview user interface.
 6. A system comprising: aprocessor; and a memory storing instructions that, when executed by theprocessor, configure the processor to perform operations comprising:providing, by a messaging application, a capture user interface forcapturing a video to generate a media content item; automaticallyswitching, by the messaging application and upon completion of capturingthe video, from the capture user interface to a preview user interfacefor previewing and editing the captured video in order to generate themedia content item, the preview user interface including an interfaceelement to select a playback option, from among plural playback options,for the media content item, the preview user interface further includinga preview bar in a contracted state, the contracted state including afirst set of frames of the captured video and omitting front and backhandles, wherein the preview bar is automatically displayed in thecontracted state based on a length of the captured video exceeding apreset length; receiving, by the messaging application and via theinterface element, user input selecting the preview bar; and updating,by the messaging application and in response to the receiving, thepreview bar from the contracted state to an expanded state, the expandedstate including a second set of frames of the captured video which islarger than the first set of frames, further including a front handleand a back handle respectively positioned in front and in back of thesecond set of frames, each of the front handle and the back handle beingselectable to trim the captured video, and further including a splittingelement which is user-selectable to split the captured video intoseparate video clips.
 7. The system of claim 6, wherein the pluralplayback options comprise looping the captured video, bouncing thecaptured video or playing back the captured video a single time.
 8. Thesystem of claim 6, wherein the front and back handles are selectable toscrub through the captured video.
 9. The system of claim 6, wherein eachvideo clip of the separate video clips is presented with at least one ofrespective front and back handles for trimming the video clip, arespective splitting element for splitting the video clip, and arespective delete button for deleting the video clip.
 10. The system ofclaim 6, wherein the preview user interface further includes a playbackregion for looping playback of the captured video, and wherein theplayback region is user selectable to remove the preview bar fromdisplay within the preview user interface.
 11. A non-transitorycomputer-readable storage medium, the computer-readable storage mediumincluding instructions that when executed by a computer, cause thecomputer to perform operations comprising: providing, by a messagingapplication, a capture user interface for capturing a video to generatea media content item; automatically switching, by the messagingapplication and upon completion of capturing the video, from the captureuser interface to a preview user interface for previewing and editingthe captured video in order to generate the media content item, thepreview user interface including an interface element to select aplayback option, from among plural playback options, for the mediacontent item, the preview user interface further including a preview barin a contracted state, the contracted state including a first set offrames of the captured video and omitting front and back handles,wherein the preview bar is automatically displayed in the contractedstate based on a length of the captured video exceeding a preset length;receiving, by the messaging application and via the interface element,user input selecting the preview bar; and updating, by the messagingapplication and in response to the receiving, the preview bar from thecontracted state to an expanded state, the expanded state including asecond set of frames of the captured video which is larger than thefirst set of frames, further including a front handle and a back handlerespectively positioned in front and in back of the second set offrames, each of the front handle and the back handle being selectable totrim the captured video, and further including a splitting element whichis user-selectable to split the captured video into separate videoclips.
 12. The computer-readable medium of claim 11, wherein the pluralplayback options comprise looping the captured video, bouncing thecaptured video or playing back the captured video a single time.